|
![](/i/fill.gif) |
Vahur Krouverk wrote:
> Can You explain Your work? What do You mean by "reduce the size of any triangle
> mesh file"? I've tried by myself patching PovRay to be able to read binary mesh
> files (my custom format, where textual representation was replaced with direct
> binary representation of float numbers). This drop parsing time for my scene from
> 80 to 30 second and files were smaller as well (by 40 % if I remember correctly).
The new syntax is still in text format, but it uses indices & vertex lists, similar
to how 3DS files work. I'm not sure of how much space is saved, but it should be
OK. Being able to read a binary format might also be good, but I don't think that
introducing ANOTHER 3D format would be such a good idea. Maybe if we could get
POV to read DXF... but then there are copyright issues to deal with.
> May-be it's easier to use converter instead of patching PovRay. I don't know, how
> long it will take to patch Povray, for as I said, I'm not expert in this field. And
> I don't know, whether it will produce better outcome (parsing time will be
> supposedly smaller, but if rendering time goes high, then it is useless).
Patching POV with non-trimmed would involve quite a bit of stuff (but should be
possible if a few people work on it).
-Nathan Kopp
Post a reply to this message
|
![](/i/fill.gif) |